home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Wildcat Files 2
/
The Wildcat Files 2 (Arsenal Computer).ISO
/
desq
/
wildcat.tec
< prev
next >
Wrap
Text File
|
1994-07-18
|
10KB
|
192 lines
ID:WC DESQview and Wildcat BBS
Quarterdeck Technical Note #282 Filename: WILDCAT.TEC
by Brian P. Doud CompuServe: WILDCT.TEC
Last revised: 6/28/94 Category: DV
Subject: Troubleshooting and configuring Wildcat!BBS under DESQview.
OVERVIEW
There are several issues that need to be taken into account when setting
up a BBS (Bulletin Board System) under DESQview. Though Wildcat! is the focus
here, many of the concepts presented here may apply to other DESQview-aware
BBS systems as well. In addition, much of the information covered here can be
applied to DESQview/X.
The topic of running a multi-node BBS inside DESQview is often confusing,
primarily because of the lack of information available on the subject. With
this technote, it's hoped that some of the fears and problems associated with
BBSes in DV will be alleviated. There are many issues not covered here which
more than likely have to do with the configuration of the BBS in question,
rather than DV or DVX.
Some of the confusion associated with BBSes is in the terminology, so a
few of the commonly used terms will be clarified throughout this document.
NODES
A BBS node is the way for a caller to contact a BBS. It acts almost like
an interactive answering machine, picking up calls as they come in, then
sending information back to the caller. On a Wildcat!BBS, the node program
(WILDCAT.EXE) is started within a batch file, which assigns a node id to each
node so the BBS software can tell the difference between them. The batch
files for multi-node BBSes are usually identical except for the node id, so
great care must be taken to use one node id per batch file. Repeating id's
over several files can result in incorrect operation of the BBS.
Though a lot goes on in a node's operation, it can be treated pretty much
like any other program that is run in DV. There are two main processes that
go on when a node starts that can be related to DESQview. The first is the
loading of the node program itself. It requires some minimum amount of
memory, so it is important to make sure that the system has been configured to
provide DESQview windows as much memory as possible.
The other thing that occurs is the initialization of the modem. When a
problem occurs with the modem's initialization or operation, it can come from
a variety of sources, so the true nature of the problem must first be
determined.
MODEMS
Modem problems are, in the vast majority of cases, an issue of hardware
rather than software, so DESQview is usually out of the equation when trouble
arises. However, there are some things to keep in mind when the BBS isn't
functioning correctly as a result of a modem problem.
The first thing to do once the BBS has been set up and testing of the
nodes begins is to run the nodes individually in DOS. This will ensure that
the node works with the existing hardware and software configuration. This
way, it can be determined whether any problems are related to DESQview. If a
new problem arises after the BBS has been operational for some time, this
procedure should be tried again, to make sure the problem is not related to
DESQview.
DESQVIEW CONFIGURATION
When setting up a BBS under DESQview, the first thing that should be
checked is DESQview Setup, particularly the Performance section; this will
help to prevent problems down the line. For best results, the Task Processing
Time (Clock Ticks) should be set to 2 foreground/2 background on a 486
machine, 3 foreground / 3 background on a 386 machine. Also, Optimize
Communications should be set to Y for the benefit of high speed modems.
Additionally, there are several settings within the DESQview .DVP file
for the nodes which must be carefully set. What follows are some of the key
.DVP settings, and some notes about each (the option in parentheses indicates
the DVX wording).
- Memory Size (DV and DVX): tells DV the minimum amount of
conventional memory necessary to start an application. The
Wildcat! manual recommends 350K, though this number may be
changed if necessary.
- Program (DOS Command): specifies the .EXE, .COM, or .BAT file
that is run. When running a multi-node setup, make sure that
each .DVP is using its own unique batch file. Failure to do
this can result in the conflict between nodes. This cannot
be stressed enough; many of the problems between nodes are the
result of more than one node using the same batch file--this
WILL cause a problem, and must be avoided.
- Writes Directly to screen (DV and DVX): tells DV whether the
program writes its information directly to the screen rather
than allowing DV to manage the video. This option is an
informational setting; it tells DV how a program operates,
rather than what DV should do to the program. Since Wildcat!
is DESQview-aware, this option should be set to N.
- Virtualize text/graphics (Virtualize text): tells DV whether
it should try to put the program in a window. Since Wildcat!
is DESQview-aware, this option should also be set to N.
- (Display DOS Window): this DVX-only option specifies whether
a DOS window should be displayed before the application attempts
to start. While this is generally unnecessary for X Window
applications, it should be toggled on for DOS programs.
- Uses its own colors (DV and DVX): set this option to Y in DV or
toggle it on in DVX to allow the node to start in its normal
display colors. Setting this option to N will cause the window
to display text in the colors set in DESQview Setup.
- Can be swapped out (DV only): communications programs should not
be swapped to disk, as they will lose the phone connection; this
option must be set to N.
These are the most notable settings in DV and DVX that must be
specifically configured. For more information, please consult the Wildcat!
documentation.
MEMORY
Memory in DESQview is arguably the most difficult aspect of DESQview to
configure. Fortunately, BBS node software doesn't usually require an
unusually large amount of memory. The advantage of running a multi- node BBS
under DESQview is the ability to run other applications concurrently with the
BBS software. This advantage can be compromised when that application
requires significantly more memory than the node software.
A common hardware device used in conjunction with a multi-node BBS is an
intelligent multiport board, such as that offered by DigiBoard or Arnet. This
device arbitrates COM ports through an interface board rather than through
standard serial ports. This is certainly an advantage for BBSes of 5 or more
nodes in size, as it eliminates the need for several multiport serial cards. A
slight disadvantage is that these boards use a 64K area between 640-1024K to
function. This limits the amount of High RAM available, as the area will need
to be excluded with a parameter on the QEMM386.SYS line in the CONFIG.SYS
file.
In order to assist in any way possible, we have other technotes which
cover this process in greater detail. There are two technotes that discuss
the subject of getting more memory for each DESQview window. For DV, you need
#161 - WINSIZE.TEC; for DVX, #252 - MAXWINDO.TEC. Whichever one you need, the
problem will likely be corrected by following the suggestions enclosed.
DOORS
A door, simply put, is a DOS shell. A door is the method for DOS
applications to be run in a node. There are many types of doors, ranging from
the most common--a mail door--to innumerable game doors. The interface to
this is frequently a TSR that is run in the batch file that starts the node.
Front Door is one such type of interface program, though there are others
available. A frequent exception to this is mail doors, which are generally
handled by the BBS software itself, without the need for a door interface
program.
With regard to DESQview, the most common problem is that of the door
program exiting shortly after startup, or simply not loading at all. At
times, an error message is seen which indicates a memory problem. Usually the
reason for this is that the program is requiring an amount of conventional
memory that just isn't available in that window. This problem should be
handled in the same manner as any program that has insufficient memory to run
under DV or DVX: get more memory to the window(s).
FINAL NOTES
As mentioned previously, the information in this technote is geared
toward troubleshooting problems with multi-node BBSes, particularly Wildcat!,
in DESQview and DESQview/X. Some of the problems encounted, most notably with
hardware, are independent of the multitasker. In those situations, it is
advisable to consult the manufacturer of the particular hardware in order to
get it properly configured.
******************************************************************************
* This technical note may be copied and distributed freely as long as it *
* is distributed in its entirety and it is not distributed for profit. *
* Copyright (C) 1994 by Quarterdeck Office Systems *
************************** E N D O F F I L E *****************************